home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Stac Reachout 7
/
Stac Reachout 7.iso
/
STACFAX
/
8704.TXT
< prev
next >
Wrap
Text File
|
1997-01-31
|
13KB
|
215 lines
-----------------------------------------------------------------
STAC NOTE STAC NOTE
TIPS FOR CONFIGURING REACHOUT WITH NETWARE CONNECT
(Applies to ReachOut versions 4.X, 5.X)
STAC FAX 8704 (1/96)
-----------------------------------------------------------------
BACKGROUND
This document provides information on configuring ReachOut with
Netware Connect (NWC) versions 1.0 or 2.0. Note that if you are
using NWC version 2, you must use VLMÆs rather than NETX. Novell
maintains a FaxBack service at (801) 429-7642. Contact Novell's
FaxBack service for information on configuring Netware Connect
version 1.0 or for background and configuration information for
Netware Connect version 2.0. Also, be sure to read the tips at
the end of the document to help you with troubleshooting, or if
you are setting up ReachOut as a Host.
SOLUTION
- Configuring ReachOut ver 5 and Win2NCS.
- Configuring ReachOut and Netware Connect with NASI TSR in
Windows.
- Configuring ReachOut and Netware Connect in DOS.
Configuring ReachOut ver 5 and Win2NCS
Note: ReachOut version 4 does not work with Win2NCS. You must
upgrade to ReachOut version 5 to use Win2NCS. The ReachOut
version 5 configuration is simpler and is considerably faster,
especially during file transfers. Upgrading to ReachOut version 5
is strongly recommended.
1. Install Win2NCS version 1.11c or later. See StacFax 8512 or
your Novell provider for information on obtaining the latest
version of Win2NCS.
2. Run the Win2NCS Mapping Utility. Under Global Mapping
Options, set Hardware Flow Control to Always. If you are
using Netware 4.X, set Prompt User for 4.X Context to
Enabled.
3. The background of the mapping utility should be blue. If it
is red, open Options and Enable NASI Redirection.
4. Open Map Communications Ports. Check the bottom part of the
window under Available Services. If the only entries are
<Any> <Any> <Any>, then Win2NCS is not set up properly.
Contact your Novell provider for assistance.
5. Map an available com port with a Server name and a General
name.
6. Open the ReachOut Configuration icon. Select Modem as
Connection Type. If you are setting up ReachOut as a Host,
see Tip 4 on the last page.
7. At the next screen, choose the com Port being redirected by
Win2NCS. Also select your modem type from the modem list, or
choose A Hayes Compatible modem.
8. Open the Advanced Settings and ensure that Data Compression
and Windows COMM.DRV Compatible are both checked.
9. Accept the configuration by clicking on OK all the way out.
ReachOut and Netware Connect are now configured.
Configuring ReachOut and Netware Connect with NASI TSR in Windows
IMPORTANT: Whenever you are asked to enter Server, Service or
Port names, remember that they are CASE-SENSITIVE! To prevent
errors, we recommend using all caps.
If you are setting up ReachOut as a Host, see Tip 4 on the last
page.
1. Load NASI. If you are using Netware 4.X, make sure that you
use a valid user name and password from the Directory Tree.
If you are using Netware 3.X, make sure you get the user
name and password from the Bindery of the Netware Connect
Server. If you use the switch /V=n on the NASI command line,
use at least a 3 (/V=3). This will reduce the NASI TSR size
by approximately 20K.
2. Test NASI by running NASIDIAG. Select option two, List
Available NCS Ports. If no ports are listed, NASI is not
properly configured. Consult your Netware provider for
assistance in loading and configuring NASI.
3. Open ReachOut's Configuration icon. From the Communications
section, choose Netware Connect. Then click on Setup.
4 For the Connect Inbound Server Name enter the first eight
characters of the server name. Double check your spelling!
Most calls to Product Support are a result of misspelled
server names!
5. For the Connect Inbound Service Name enter the name of the
Shared Dial-in or Inbound group that you created in the NWC
Configuration. See Tip 4 at the end of this document.
6. Leave the Any box checked for the Inbound Connect Port Name.
7. For Outbound Connect Server Name enter the name of the NWC
Server that will be used for dialing out of the network.
8. For the Outbound Connect Service Name enter a valid General
Name that you created in the NWC Configuration. Do not use
the General Name for Shared Dial-in Ports or the Inbound
Dial-in group specified in NWC Configuration.
9. Leave the Any box checked for the Outbound Connect Port
Name.
10. Accept the configuration by clicking on OK all the way out.
ReachOut and Netware Connect are now configured.
Configuring ReachOut and Netware Connect in DOS
IMPORTANT: Whenever you are asked to enter Server, Service or
Port names, remember that they are CASE-SENSITIVE! To prevent
errors, we recommend using all caps.
If you are setting up ReachOut as a Host, see Tip 4 on the last
page.
1. Load NASI. If you are using Netware 4.X, make sure that you
use a valid user name and password from the Directory Tree.
If you are using Netware 3.X, make sure you get the user
name and password from the Bindery of the Netware Connect
Server. If you use the switch /V=n on the NASI command line,
use at least a 3 (/V=3). This will reduce the NASI TSR size
by approximately 20K.
2. Test NASI by running NASIDIAG. Select option two, List
Available NCS Ports. If no ports are listed, NASI is not
properly configured. Consult your Netware provider for
assistance in loading and configuring NASI.
3. Run ReachOut's Host or Viewer. From Preferences choose
Communications Setting, then Comm Port. Select Netware
Connect ACS, which displays the screen for specifying
services for the Netware Connect interface.
4. For the Connect Inbound Server Name enter the first eight
characters of the server name. Double check your spelling!
Most calls to Product Support are a result of misspelled
server names!
5. For the Connect Inbound Service Name enter the name of the
Shared Dial-in or Inbound group that you created in the NWC
Configuration. See Tip 4 at the end of this document.
6. Leave an asterisk for the Connect Inbound Port Name.
7. For Connect Outbound Server Name enter the name of the NWC
Server that will be used for dialing out of the network.
8. For the Outbound Connect Service Name enter a valid General
Name that you created in the NWC Configuration. Do not use
the General Name for Shared Dial-in Ports or the Inbound
Dial-in group specified in NWC Configuration.
9. Leave an asterisk for the Connect Outbound Port Name.
10. Save the changes and exit to DOS.
11. Examine the GxM batch file. The line that loads the
communications TSR is usually the second line. It should
load the RCHACS TSR. It should look something like this:
C:\REACHOUT\RCHACS NAME=<name>
If not, edit the file to load RCHACS. Also, in the GVM batch
file, make the same change in the line that unloads the TSR.
Tips on using ReachOut with Netware Connect
1. When using ReachOut with Netware Connect in a configuration
where the processors are being rebooted after disconnect, a
user might find that Netware Connect is dropping the session
from its Service Selector List. If so, a delay of
approximately 20-30 seconds before loading NASI should allow
enough time for Netware Connect to release the virtual
connection between NWC and the recently rebooted host PC. An
easy way to accomplish this delay is with DOS 6.x's CHOICE
command in the AUTOEXEC.BAT file i.e.: CHOICE /C:. /N
/T:.,20
2. If you are experiencing difficulty getting ReachOut to open
the communications channel and Netware Connect is setup
properly, according to the above procedures, the file
MODEM.RCH may be corrupt. Delete the file in the REACHOUT
directory. Then reenter the information in ReachOut setup.
i.e.: Modem type, Netware connect ports, etc.
3. If you are using Netware ConnectÆs ARAS option, you may get
a "NO CARRIER" back from your modem before getting prompted
for your Netware Connect username. This appears to be a
problem between ARAS and the v.42bis error-correction
protocol that some modems use. The symptom is visible from
any terminal program calling into the Netware Connect ACS
Server. The issue is most prominent in the Hayes Optima
series of modems.
Disable the modem's v.42bis error-correction protocol. Do
this by changing or adding the appropriate commands to your
modemÆs reset string by opening Configuration, Advanced
Settings, Modem Config. Refer to your modem's documentation
for the proper commands to disable v.42bis error correction.
4. If you are using ReachOut as a Host through NWC, configure
ReachOut as follows:
a. If using the NASI TSR, make sure that the inbound service
specified in ReachOutÆs NWC configuration is the same as the
General name for Shared Dial-in Ports on the NWC server. To
check on the General name, from the NWC Console select
'Configure NWC', 'Services', 'NCS'. If it is blank, have
your Network Administrator specify or create a Dial-in
group. Version 1.x of Netware Connect simply calls this
setting the 'Dial-in Group' under 'Configure NWC',
'Configure service', 'NCS', 'Configure NCS'. Also, make sure
that the same screen shows that the 'Modem Independent
Group' is blank.
b. If using Win2NCS, make sure that the General name
specified in the NASI mapping utility is the same as the
General name for Shared Dial-in Ports as specified above.
5. If you are using ReachOut version 5.03, you may get the message
'Failed to connect to ReachOut Host. Do you want to start the
terminal emulator?' If so, you must setup or edit your
phonebook entries as terminal types. Then, once you go through
the NWC login, you will automatically be passed off to a
ReachOut Host.
a. To edit a phonebook entry as the terminal type: Open the
Viewer and click on the Remote Control button. The phonebook
list will be displayed. The Type column should have a æTÆ. If
not, click on the Edit button, then check the Terminal
Emulation Entry box at the bottom of the screen.
b. To determine if you have ReachOut 5.03 look in your REACHOUT
directory for HOSTMENU.EXE. If the date and time of the file
are 12/1/95 at 5:03am, you have ReachOut version 5.03. You may
update to 5.03 by downloading the file RO5UP.EXE from the Stac
BBS at (619) 794-3711, or from the Internet at www.stac.com.
-----------------------------------------------------------------
Copyright 1996 Stac Electronics